16 Managing Pluggable Databases

Prerequisites

• Oracle Software Library (Software Library) must be set up in Cloud Control.

  For information on how to set up Software Library in Cloud Control, refer Setting Up Oracle Software Library.

• The CDB within which you want to create a PDB must exist, and must be a Cloud Control target.

  Note:

  For information on how to create a new CDB, refer to Chapter 15.

• The CDB (within which you want to create a PDB) must not be in read-only, upgrade, or downgrade mode.

• The target host user must be the owner of the Oracle home that the CDB (within which you want to create the PDB) belongs to.

Procedure

To create a new PDB in a CDB, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning. In the Database Provisioning page, in the Related Links section of the left menu pane, click Provision Pluggable Databases.

   Note:

   You can also access the Provision Pluggable Database Console from the home page of the CDB. To do so, in the CDB's home page, from the Oracle Database menu, select Provisioning, then select Provision Pluggable Database.

2. In the Provision Pluggable Database Console, in the CDB section, select the CDB within which you want to create new PDBs.

   Note:

   Skip this step if you have accessed the Provision Pluggable Database Console from the CDB's home page.

3. In the PDB Operations section, select Create Pluggable Databases.

4. Click Launch.

   Figure 16-2 displays the Provision Pluggable Database Console.

   Figure 16-2 Provision Pluggable Database Console

   
   

   Note:

   You will be prompted to log in to the database if you have not already logged in to it through Enterprise Manager. Make sure you log in using sysdba user account credentials.

5. In the Source page of the Create Pluggable Database Wizard, in the Source Type section, select Create a new PDB.

6. In the CDB Host Credentials section, select or specify the target CDB Oracle home owner host credentials. If you have already registered the credentials with Enterprise Manager, you can select Preferred or Named. Otherwise, you can select New and enter the credentials.

   Figure 16-3 displays the Source page.

   Figure 16-3 Creating a New Pluggable Database: Source Page

   
   

7. Click Next.

8. In the Identification page, enter a unique name for the PDB you are creating.

   If you prefer to create more than one PDB in this procedure, then select Create Multiple PDBs, and set the number of PDBs you want to create. Note that you can create a maximum of 252 PDBs.

   Note:

   If you choose to create multiple PDBs, then the unique name you enter here is used as a prefix for all PDBs, and the suffix is a numeric value that indicates the count of PDBs.

   For example, if you create five PDBs with the name accountsPDB, then the PDBs are created with the names accountsPDB1, accountsPDB2, accountsPDB3, accountsPDB4, and accountsPDB5.

9. In the PDB Administrator section, enter the credentials of the admin user account you need to create for administering the PDB.

   Figure 16-4 displays the Identification page.

   Figure 16-4 Creating a New Pluggable Database: Identification Page

   
   

   Note:

   If you choose to create multiple PDBs, then for each PDB an admin user account is created with the same set of credentials you enter here. So multiple admin user accounts are created, one per PDB, but the user accounts have the same credentials.

10. Click Next.

11. In the Storage page, select the type of location where you want to store the datafiles.

    • If the target CDB (CDB in which you are creating the PDB) is enabled with Oracle Managed Files and if you want to use the same, then select Use Oracle Managed Files (OMF).

    • If you want to enter a custom location, then select Use Common Location for PDB Datafiles. Select the storage type and the location where the datafiles can be stored.

12. In the Temporary Working Directory section, enter a location where the temporary files generated during the PDB creation process can be stored.

13. In the Custom Scripts section, select a custom SQL script you want to run as part of this procedure, once the PDB is created.

    Figure 16-5 displays the Storage page.

    Figure 16-5 Creating a New Pluggable Database: Storage Page

    
    

14. Click Next.

15. In the Schedule page, enter a unique deployment procedure instance name and a schedule for the deployment. The instance name you enter here helps you identify and track the progress of this procedure on the Procedure Activity page.

    If you want to run the procedure immediately, then retain the default selection, that is, Immediately. Otherwise, select Later and provide time zone, start date, and start time details.

    You can optionally set a grace period for this schedule. A grace period is a period of time that defines the maximum permissible delay when attempting to run a scheduled procedure. If the procedure does not start within the grace period you have set, then the procedure skips running. To set a grace period, select Grace Period, and set the permissible delay time.

    Figure 16-6 displays the Schedule page.

    Figure 16-6 Creating a New Pluggable Database: Schedule Page

    
    

16. Click Next.

17. In the Review page, review the details you have provided for the deployment procedure. If you are satisfied with the details, click Submit.

    If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

    Figure 16-7 displays the Review page.

    Figure 16-7 Creating a New Pluggable Database: Review Page

    
    

18. In the Procedure Activity page, view the status of the procedure. Click the Status link for each step to view the details of the execution of each step. You can click Debug to set the logging level to Debug, and click Stop to stop the procedure execution.

    Figure 16-8 displays the Procedure Activity page.

    Figure 16-8 Creating a New Pluggable Database: Procedure Activity Page

    
    

    When you create a new PDB, the Enterprise Manager job system creates a Create Pluggable Database job. For information about viewing the details of this job, refer Viewing Create Pluggable Database Job Details.

Prerequisites

Before plugging in an unplugged PDB, ensure that you meet the following prerequisites:

• Oracle Software Library (Software Library) must be set up in Cloud Control.

  For information on how to set up Software Library in Cloud Control, refer Setting Up Oracle Software Library.

• The target CDB (the CDB within which you want to plug in the unplugged PDB) must exist, and must be a Cloud Control target.

  Note:

  For information on how to create a new CDB, refer to Chapter 15.

• The target CDB must not be in read-only, upgrade, or downgrade mode.

• The XML file that describes the unplugged PDB, and the other files associated with the unplugged PDB, such as the datafiles and the wallet file, must exist and must be readable.

• The target host user must be the owner of the Oracle home that the CDB (within which you want to plug in the unplugged PDB) belongs to.

• The platforms of the source CDB host (the host on which the CDB that previously contained the unplugged PDB is installed) and the target CDB host (the host on which the target CDB is installed) must have the same endianness, and must have compatible database options installed.

• The source CDB (the CDB that previously contained the unplugged PDB) and the target CDB must have compatible character sets and national character sets. Every character in the source CDB character set must be available in the target CDB character set, and the code point value of every character available in the source CDB character set must be the same in the target CDB character set.

Procedure

To plug in an unplugged PDB to a CDB, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning. In the Database Provisioning page, in the Related Links section of the left menu pane, click Provision Pluggable Databases.

   Note:

   You can also access the Provision Pluggable Database Console from the home page of the CDB. To do so, in the CDB's home page, from the Oracle Database menu, select Provisioning, then select Provision Pluggable Database.

2. In the Provision Pluggable Database Console, in the CDB section, select the CDB to which you want to add the unplugged PDBs.

   Note:

   Skip this step if you have accessed the Provision Pluggable Database Console from the CDB's home page.

3. In the PDB Operations section, select Create Pluggable Databases.

4. Click Launch.

   Figure 16-9 displays the Provision Pluggable Database Console.

   Figure 16-9 Provision Pluggable Database Console

   
   

   Note:

   You will be prompted to log in to the database if you have not already logged in to it through Enterprise Manager. Make sure you log in using sysdba user account credentials.

5. In the Source page of the Create Pluggable Database Wizard, in the Source Type section, select Plug an unplugged PDB.

6. In the CDB Host Credentials section, select or specify the target CDB Oracle home owner host credentials. If you have already registered the credentials with Enterprise Manager, you can select Preferred or Named. Otherwise, you can select New and enter the credentials.

   Figure 16-10 displays the Source page.

   Figure 16-10 Plugging In an Unplugged Pluggable Database: Source Page

   
   

7. Click Next.

8. In the Identification page, enter a unique name for the PDB you are plugging in.

   Select Create As Clone to ensure that Oracle Database generates unique PDB DBID, GUID, and other identifiers expected for the new PDB.

   If you prefer to create more than one PDB in this procedure, then select Create Multiple PDBs, and set the number of PDBs you want to create. Note that you can create a maximum of 252 PDBs.

   Note:

   If you choose to create multiple PDBs, then the unique name you enter here is used as a prefix for all PDBs, and the suffix is a numeric value that indicates the count of PDBs.

   For example, if you create five PDBs with the name accountsPDB, then the PDBs are created with the names accountsPDB1, accountsPDB2, accountsPDB3, accountsPDB4, and accountsPDB5.

9. In the PDB Administrator section, do one of the following to administer the PDB:

   • If you prefer to use the admin user account that was created as part of the source PDB that you are plugging in, then deselect Create Pluggable Database Administrator.

   • If you want to create a brand new admin user account for the PDB you are plugging in, then select Create Pluggable Database Administrator, and enter the desired credentials.

   Note:

   If you choose to create multiple PDBs, then for each PDB an admin user account is created with the same set of credentials you retain or enter here. So multiple admin user accounts are created, one per PDB, but the user accounts have the same credentials.

   To lock and expire all the users in the newly created PDB, (except the newly created Admin), select Lock All Existing PDB Users.

   Figure 16-11 displays the Identification page.

   Figure 16-11 Plugging In an Unplugged Pluggable Database: Identification Page

   
   

10. In the PDB Template Location section, select the location where the source PDB's template is available, and then select the type of PDB template.

    • If the PDB template is available on your CDB host (CDB to which you are plugging in the unplugged PDB), then select Target Host File System.

      • If the PDB template is a single archive file—a TAR file with datafiles and metadata XML file included in it, then select Create Pluggable Database from Pluggable Database Archive, then select the PDB template.

      • If the PDB template is a PDB file set—a separate DFB file with all the datafiles and a separate metadata XML file, then select Create Pluggable Database using Pluggable Database File Set, then select the DBF and XML files.

      • If you want to plug in a PDB using the PDB metadata XML file and the existing datafiles, then select Create Pluggable Database using Metadata file.

    • If the PDB template is available in Oracle Software Library (Software Library), then select Software Library, then select the component in the Software Library that contains the PDB template.

    Figure 16-12 displays the PDB Template Location section of the Identification page.

    Figure 16-12 Plugging In an Unplugged Pluggable Database: PDB Template Location Section

    
    

11. Click Next.

12. In the Storage page, do one of the following:

    • In the previous page, if you chose to create the PDB from a pluggable database archive (single TAR file) or using a pluggable database file set (DFB file and an XML file), then select the type of location where you want to store the target datafiles for the PDB you are plugging in.

      • If the target CDB (CDB to which you are plugging in the unplugged PDB) is enabled with Oracle Managed Files and if you want to use the same, then select Use Oracle Managed Files (OMF).

      • If you want to enter a common custom location, then select Use Common Location for PDB datafiles. Select the storage type and the location where the datafiles can be stored.

    • In the previous page, if you chose to create the PDB using a pluggable database template (XML file only), then do the following:

      In the Pluggable Database File Location section, validate the locations mapped for the datafiles. If they are incorrect, correct the paths. Alternatively, if you have a single location where the datafiles are all available, then enter the absolute path in the Set Common Source File Mapping Location field, and click Set.

      You can choose to store the target datafiles for the PDB you are plugging in, in the same location as the source datafiles. However, if you want the target datafiles to be stored in a different location, then select Copy Datafiles, and select the type of location:

      • If the target CDB (CDB to which you are plugging in the unplugged PDB) is enabled with Oracle Managed Files and if you want to use the same, then select Use Oracle Managed Files (OMF).

      • If you want to enter a common custom location, then select Use Common Location for Pluggable Database Files. Select the storage type and the location where the datafiles can be stored.

      • If you prefer to use different custom locations for different datafiles, then select Customized Location, and enter the custom location paths.

13. In the Temporary Working Directory section, enter a location where the temporary files generated during the PDB creation process can be stored.

14. In the Custom Scripts section, select a custom SQL script you want to run as part of this procedure, once the PDB is plugged in.

    If the script is available in the Software Library, select Select from Software Library, then select the component that contains the custom script.

    Figure 16-13 displays the Storage page.

    Figure 16-13 Plugging In an Unplugged Pluggable Database: Storage Page

    
    

15. Click Next.

16. In the Schedule page, enter a unique deployment procedure instance name and a schedule for the deployment. The instance name you enter here helps you identify and track the progress of this procedure on the Procedure Activity page.

    If you want to run the procedure immediately, then retain the default selection, that is, Immediately. Otherwise, select Later and provide time zone, start date, and start time details.

    You can optionally set a grace period for this schedule. A grace period is a period of time that defines the maximum permissible delay when attempting to run a scheduled procedure. If the procedure does not start within the grace period you have set, then the procedure skips running. To set a grace period, select Grace Period, then set the permissible delay time.

    Figure 16-14 displays the Schedule page.

    Figure 16-14 Plugging In an Unplugged Pluggable Database: Schedule Page

    
    

17. Click Next.

18. In the Review page, review the details you have provided for the deployment procedure. If you are satisfied with the details, click Submit.

    If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

    Figure 16-15 displays the Review page.

    Figure 16-15 Plugging In an Unplugged Pluggable Database: Review Page

    
    

19. In the Procedure Activity page, view the status of the procedure. Click the Status link for each step to view the details of the execution of each step. You can click Debug to set the logging level to Debug, and click Stop to stop the procedure execution.

    Figure 16-16 displays the Procedure Activity page.

    Figure 16-16 Plugging In an Unplugged Pluggable Database: Procedure Activity Page

    
    

    When you plug in an unplugged PDB, the Enterprise Manager job system creates a Create Pluggable Database job. For information about viewing the details of this job, refer Viewing Create Pluggable Database Job Details.

Prerequisites

To clone a PDB to the source CDB, you must meet the following prerequisites:

• Oracle Software Library (Software Library) must be set up in Cloud Control.

  For information on how to set up Software Library in Cloud Control, refer Setting Up Oracle Software Library.

• The source PDB (the PDB that you want to clone) must exist, and must be a Cloud Control target.

  Note:

  For information on how to create a new PDB, refer to Creating a New Pluggable Database.

• The source PDB must be open.

• The source CDB must not be in read-only, upgrade, or downgrade mode.

• The target host user must be the owner of the Oracle home that the source CDB belongs to.

Procedure

To clone an existing PDB to the source CDB, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning. In the Database Provisioning page, in the Related Links section of the left menu pane, click Provision Pluggable Databases.

   Note:

   You can also access the Provision Pluggable Database Console from the home page of the CDB. To do so, in the CDB's home page, from the Oracle Database menu, select Provisioning, then select Provision Pluggable Database.

2. In the Provision Pluggable Database Console, in the CDB section, select the source CDB, that is, the CDB containing the PDB that you want to clone.

   Note:

   Skip this step if you have accessed the Provision Pluggable Database Console from the CDB's home page.

3. In the PDB Operations section, select Create Pluggable Databases.

4. Click Launch.

   Figure 16-17 displays the Provision Pluggable Database Console.

   Figure 16-17 Provision Pluggable Database Console

   
   

   Note:

   You will be prompted to log in to the database if you have not already logged in to it through Enterprise Manager. Make sure you log in using sysdba user account credentials.

5. In the Source page of the Create Pluggable Database Wizard, in the Source Type section, select Clone PDB. Then, select the PDB you want to clone.

6. In the CDB Host Credentials section, select or specify the source CDB Oracle Home owner host credentials. If you have already registered the credentials with Enterprise Manager, you can select Preferred or Named. Otherwise, you can select New and enter the credentials.

   Figure 16-18 displays the Source page.

   Figure 16-18 Cloning a Pluggable Database: Source Page

   
   

7. Click Next.

8. In the Identification page, enter a unique name for the PDB you are cloning.

   If you prefer to create more than one PDB in this procedure, then select Create Multiple PDBs, and set the number of PDBs you want to create. Note that you can create a maximum of 252 PDBs.

   Note:

   If you choose to create multiple PDBs, then the unique name you enter here is used as a prefix for all the cloned PDBs, and the suffix is a numeric value that indicates the count of PDBs.

   For example, if you create five PDBs with the name accountsPDB, then the PDBs are created with the names accountsPDB1, accountsPDB2, accountsPDB3, accountsPDB4, and accountsPDB5.

9. In the PDB Administrator section, do one of the following to administer the PDB:

   • If you prefer to use the admin user account that was created as part of the source PDB that you are cloning, then deselect Create Pluggable Database Administrator.

   • If you want to create a brand new admin user account for the PDB you are cloning, then select Create Pluggable Database Administrator, and enter the desired credentials.

   Figure 16-19 displays the Identification page.

   Figure 16-19 Cloning a Pluggable Database: Identification Page

   
   

   Note:

   If you choose to create multiple PDBs, then for each PDB an admin user account is created with the same set of credentials you retain or enter here. So multiple admin user accounts are created, one per PDB, but the user accounts have the same credentials.

10. In the Source CDB Login Credentials section, select or specify the login credentials of the source CDB. If you have already registered the credentials with Enterprise Manager, you can select Preferred or Named. Otherwise, you can select New and enter the credentials.

    The credentials are used to bring the source PDB to read-only mode before the cloning operation begins, and to restore it to the original state after the cloning operation ends.

    Figure 16-20 displays the Source CDB Login Credentials section of the Identification page.

    Figure 16-20 Cloning a Pluggable Database: Source CDB Login Credentials

    
    

11. Click Next.

12. In the Storage page, select the type of location where you want to store the datafiles for the PDB you are cloning.

    • If the source CDB is enabled with Oracle Managed Files and if you want to use the same, then select Use Oracle Managed Files (OMF).

    • If you want to enter a custom location, then select Use Common Location for PDB datafiles. Select the storage type and the location where the datafiles can be stored.

13. In the Temporary Working Directory section, enter a location where the temporary files generated during the PDB creation process can be stored.

14. In the Custom Scripts section, select a custom SQL script you want to run as part of this procedure, once the PDB is cloned.

    Figure 16-21 displays the Storage page.

    Figure 16-21 Cloning a Pluggable Database: Storage Page

    
    

15. Click Next.

16. In the Schedule page, enter a unique deployment procedure instance name and a schedule for the deployment. The instance name you enter here helps you identify and track the progress of this procedure on the Procedure Activity page.

    If you want to run the procedure immediately, then retain the default selection, that is, Immediately. Otherwise, select Later and provide time zone, start date, and start time details.

    You can optionally set a grace period for this schedule. A grace period is a period of time that defines the maximum permissible delay when attempting to run a scheduled procedure. If the procedure does not start within the grace period you have set, then the procedure skips running. To set a grace period, select Grace Period, and set the permissible delay time.

    Figure 16-22 displays the Schedule page.

    Figure 16-22 Cloning a Pluggable Database: Schedule Page

    
    

17. Click Next.

18. In the Review page, review the details you have provided for the deployment procedure. If you are satisfied with the details, click Submit.

    If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

    Figure 16-23 displays the Review page.

    Figure 16-23 Cloning a Pluggable Database: Review Page

    
    

19. In the Procedure Activity page, view the status of the procedure. Click the Status link for each step to view the details of the execution of each step. You can click Debug to set the logging level to Debug, and click Stop to stop the procedure execution.

    Figure 16-24 displays the Procedure Activity page.

    Figure 16-24 Cloning a Pluggable Database: Procedure Activity Page

    
    

    When you clone a PDB, the Enterprise Manager job system creates a Create Pluggable Database job. For information about viewing the details of this job, refer Viewing Create Pluggable Database Job Details.

Prerequisites

Before migrating a non-CDB as a PDB, ensure that you meet the following prerequisites:

• Oracle Software Library (Software Library) must be set up in Cloud Control.

  For information on how to set up Software Library in Cloud Control, refer Setting Up Oracle Software Library.

• The target CDB (the CDB to which you want to migrate a non-CDB as a PDB) must exist, and must be a Cloud Control target.

  Note:

  For information on how to create a new CDB, refer to Chapter 15.

• The target CDB must not be in read-only, upgrade, or downgrade mode.

• The database administrators of the database you want to migrate, and the target CDB must have SYSDBA privileges.

• The target host user must be the owner of the Oracle home that the target CDB belongs to.

Procedure

To migrate a non-CDB as a PDB, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning. In the Database Provisioning page, in the Related Links section of the left menu pane, click Provision Pluggable Databases.

   Note:

   You can also access the Provision Pluggable Database Console from the home page of the CDB. To do so, in the CDB's home page, from the Oracle Database menu, select Provisioning, then select Provision Pluggable Database.

2. In the Provision Pluggable Database Console, in the CDB section, select the CDB to which you want to migrate a non-CDB as a PDB.

   Note:

   Skip this step if you have accessed the Provision Pluggable Database Console from the CDB's home page.

3. In the PDB Operations section of the Provision Pluggable Database page, select the Migrate Existing Databases option and click Launch.

   Figure 16-25 displays the Provision Pluggable Database Console.

   Figure 16-25 Provision Pluggable Database Console

   
   

4. On the Database Login page, select the Credential Name from the drop-down list. Click Login.

5. On the Migrate Non-CDBs launch page, select a Data Migration Method (Export/Import or Plug as a PDB). Enter the appropriate information for the Oracle Home Credential section.

   Click Next.

   Figure 16-26 displays the Method page.

   Figure 16-26 Migrating a Non-CDB: Method Page

   
   

6. On the Database page, select a Non-CDB to be migrated. You can select more than one. Click Add. In the database pane, provide the appropriate credential, properties, export, import, and datafile location information. Click Next.

   Figure 16-27 displays how to select the non-CDB you want to migrate.

   Figure 16-27 Migrating a Non-CDB: Selecting a Non-CDB

   
   

   Figure 16-28 displays how to specify the database and database host credentials.

   Figure 16-28 Migrating a Non-CDB: Specifying Credentials

   
   

   Figure 16-29 displays how to specify the stage location for migration.

   Figure 16-29 Migrating a Non-CDB: Specifying Stage Location

   
   

   Figure 16-30 displays how to specify the PDB administrator details and datafile location.

   Figure 16-30 Migrating a Non-CDB: Specifying PDB Properties and Datafile Location

   
   

   Figure 16-31 displays how to specify the import directory.

   Figure 16-31 Migrating a Non-CDB: Specifying Import Directory

   
   

7. On the Schedule page, enter the appropriate job and scheduling details. Click Next.

   Figure 16-32 displays the Schedule page.

   Figure 16-32 Migrating a Non-CDB: Schedule Page

   
   

8. On the Review page, review all details entered. If there are no changes required, click Submit.

   Figure 16-33 displays the Review page.

   Figure 16-33 Migrating a Non-CDB: Review Page

   
   

Prerequisites

Before unplugging and dropping a PDB, ensure that you meet the following prerequisites:

• Oracle Software Library (Software Library) must be set up in Cloud Control.

  For information on how to set up Software Library in Cloud Control, refer Setting Up Oracle Software Library.

• The PDB that you want to unplug and drop must have been opened at least once.

• The target host user must be the owner of the Oracle home that the CDB (containing the PDB that you want to unplug and drop) belongs to.

Procedure

To unplug a PDB from its CDB, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning. In the Database Provisioning page, in the Related Links section of the left menu pane, click Provision Pluggable Databases.

   Note:

   You can also access the Provision Pluggable Database Console from the home page of the CDB. To do so, in the CDB's home page, from the Oracle Database menu, select Provisioning, then select Provision Pluggable Database.

2. In the Provision Pluggable Database Console, in the CDB section, select the CDB from which you want to unplug the PDBs.

   Note:

   Skip this step if you have accessed the Provision Pluggable Database Console from the CDB's home page.

3. In the PDB Operations section, select Unplug Pluggable Database.

4. Click Launch.

   Figure 16-34 displays the Provision Pluggable Database Console.

   Figure 16-34 Provision Pluggable Database Console

   
   

   Note:

   You will be prompted to log in to the database if you have not already logged in to it through Enterprise Manager. Make sure you log in using sysdba user account credentials.

5. In the Select PDB page of the Unplug Pluggable Database Wizard, in the Select Pluggable Database section, select the PDB you want to unplug. Note that the PDB once unplugged will be stopped and dropped.

6. In the CDB Host Credentials section, select or specify the target CDB Oracle Home owner host credentials. If you have already registered the credentials with Enterprise Manager, you can select Preferred or Named. Otherwise, you can select New and enter the credentials.

   Figure 16-35 displays the Select PDB page.

   Figure 16-35 Unplugging a Pluggable Database: Select PDB Page

   
   

7. In the Destination page, select the type of PDB template you want to generate for unplugging the PDB, and the location where you want to store it. The PDB template consists of all datafiles as well as the metadata XML file.

   • If you want to store the PDB template on your CDB host (CDB from where you are unplugging the PDB), then select Target Host File System.

     • If you want to generate a single archive file—a TAR file with the datafiles and the metadata XML file included in it, then select Generate PDB Archive. Select a location where the archive file can be created.

       Note:

       Oracle recommends you to select this option if the source and target CDBs are using file system for storage. This option is not supported for PDBs using ASM as storage.

     • If you want to generate an archive file set—a separate DFB file with all the datafiles and a separate metadata XML file, then select Generate PDB File Set. Select the locations where the DBF and XML files can be created.

       Note:

       Oracle recommends you to select this option if the source and target CDBs are using ASM for storage.

     • If you want to generate only a metadata XML file, leaving the datafiles in their current location, then select Generate PDB Metadata File. Select a location where the metadata XML file can be created.

   • If you want to store the PDB template in Oracle Software Library (Software Library), then select Software Library.

     • If you want to generate a single archive file—a TAR file with the datafiles and the metadata XML file included in it, then select Generate PDB Archive. If you want to generate an archive file set—a separate DFB file with all the datafiles and a separate metadata XML file, then select Generate PDB File Set. If you want to generate only a metadata XML file, leaving the datafiles in their current location, then select Generate PDB Metadata File.

     • Enter a unique PDB template name.

       The template is created in the default location that has the following format:

       Database Configuration/<db_release>/<platform>/Database Templates

       For example,

       Database Configuration/12.1.0.0.2/unix/Database Templates

     • Enter a temporary location where the archive can be created by Enterprise Manager before it is uploaded to the Software Library.

   Figure 16-36 displays the Destination page.

   Figure 16-36 Unplugging a Pluggable Database: Destination Page

   
   

8. In the Schedule page, enter a unique deployment procedure instance name and a schedule for the deployment. The instance name you enter here helps you identify and track the progress of this procedure on the Procedure Activity page.

   If you want to run the procedure immediately, then retain the default selection, that is, Immediately. Otherwise, select Later and provide time zone, start date, and start time details.

   You can optionally set a grace period for this schedule. A grace period is a period of time that defines the maximum permissible delay when attempting to run a scheduled procedure. If the procedure does not start within the grace period you have set, then the procedure skips running. To set a grace period, select Grace Period, and set the permissible delay time.

   Figure 16-37 displays the Schedule page.

   Figure 16-37 Unplugging a Pluggable Database: Schedule Page

   
   

9. Click Next.

10. In the Review page, review the details you have provided for the deployment procedure. If you are satisfied with the details, click Submit.

    If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

    Figure 16-38 displays the Review page.

    Figure 16-38 Unplugging a Pluggable Database: Review Page

    
    

11. In the Procedure Activity page, view the status of the procedure. Click the Status link for each step to view the details of the execution of each step. You can click Debug to set the logging level to Debug, and click Stop to stop the procedure execution.

    Figure 16-39 displays the Procedure Activity page.

    Figure 16-39 Unplugging a Pluggable Database: Procedure Activity Page

    
    

    When you unplug and drop a PDB, the Enterprise Manager job system creates an Unplug Pluggable Database job. For information about viewing the details of this job, refer Viewing Unplug Pluggable Database Job Details.